home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 22
/
Cream of the Crop 22.iso
/
games
/
squad146.zip
/
UTILITY.DOC
< prev
next >
Wrap
Text File
|
1996-04-11
|
5KB
|
98 lines
There are two utility program packed with Cop Squad in all versions from
v 1.43 on. The two utilities are COPUTILS.EXE (which has been distributed
since version 1.30) and COPMAINT.EXE (distributed from version 1.43 on).
This text file is a short explanantion of what these utilities are used for
and how to run them.
COPUTILS.EXE
---------------
This utility is the main utility for Cop Squad and will accomplish many
different tasks. The tasks are listed below...
1) FILL OUT/CREATE A REGISTRATION FORM ready for mailing/faxing to Phoenix
Data Systems, Inc. for registration purposes.
2) PLAYER EDITOR for Level 2 (Deluxe) registrants. Most data fields in a
player's record can be changed in cases of error, corruption, etc. The
player can also be deleted or "twitted" via this editor. A "twitted"
player's record will never be overwritten by any new players and therefore
they will remain out of the game PERMANENTLY under their original BBS log
on name.
3) RESET PLAYER DATA FILE. This task will enable you to delete the player.dat
file without having to drop to DOS to accomplish the task.
4) KEY FILE CREATION MODULE. This task will create a SQUAD.KEY file once you
have registered Cop Squad. It will properly place all the key code info
you receive into the proper format in the text based key.
5) GAME SETUP module. This task will properly setup your configuration file(s)
based on your answers to several simple questions. The setup module needs
to be run separately for EACH NODE you wish to create a .CFG file for in a
multi-node BBS setup.
6) SPONSOR INFORMATION. This task allows you to create a text file which will
place the name of any person/organization who helps you register Cop Squad
in the opening credits of the game. This type of information helps to
encourage other BBS users to assist their sysop in registering door games
they like to see/play.
7) BAD GUYS RENAMING MODULE. This task allows the sysop to rename the hard
coded "bad guys"/suspects names in the game. The sysop will not be able to
change their attributes (i.e., strength, weapons, protection, etc.) but
he/she can assign "meaningful" names to the bad guys more in line with
their locale or users.
8) ALLOW ALIASES MODULE. This task allows the sysop to determine whether or
not players will be allowed to use aliases when playing Cop Squad on the
BBS. This is accomplished by the creation of a semaphore flag which is
created or deleted based on the sysop's answer to the question posed in
this module.
COPUTILS.EXE does not require any command lline parameters to run. Simply type
COPUTILS.EXE on the command line. Registered users will have their name read
out of the key file and shareware users will see the shareware screen.
Registered users will be able to use the modules associated with their level of
registration (i.e., Player editor, deleting player.dat file, etc.). Shareware
users will not have access to any of the registered user modules in COPUTILS.
COPMAINT.EXE
-------------
** * * * * * * * * * IMPORTANT NOTE * * * * * * * * * * * * **
COPMAINT.EXE will NOT WORK with any Cop Squad version prior to version 1.35!
The reason for this is because of the player.dat file's record structures. In
order to be able to use COPMAINT.EXE you MUST upgrade to at least version
1.35. If you are upgrading from a version prior to 1.35 you must read the
information in the UPGRADE.TXT file regarding converting the player.dat
database to v.1.35 standards.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
I wrote this maintenance program which basically does the same thing as
running SQUAD.EXE (i.e., create maint.dat, delete users if requested, run the
payroll module on Fridays, etc.). In the past if someone didn't play the
game on a Friday, NO ONE got paid that week. I tried to stay away from a
separate "maintenance" program but at this time find it necessary to do so.
Simply place the COPMAINT.EXE command line in your nightly maintenance event.
The program requires a parameter which is the name of the .cfg file you use
to play the game. Therefore it will look something like this example :
COPMAINT.EXE SQUAD.CFG
Note that if you are running multi-line and have several .cfg files, you need
only to specify one of them (i.e., SQUAD1.CFG) on the command line.
This maintenance option (COPMAINT.EXE) was requested by sysops mostly so that
the payroll module would be run whether or not someone played the game on a
Friday. If you do not run COPMAINT.EXE, the internal maintenance option in
the SQUAD.EXE program will take over as it has in the past.